Greptile Summary

This PR fixes rootly incidents get/update/delete INC-xxx commands that were failing because the CLI was passing the INC- prefix verbatim to an API that only accepts a bare numeric sequential ID, UUID, or slug.

• Adds NormalizeIncidentID() in internal/api/client.go using a compiled case-insensitive regex to strip the INC- prefix from sequential IDs; UUIDs, slugs, and bare numbers pass through unchanged.
• Applies normalization to get, update, and delete commands; delete and update correctly separate displayID from the normalized incidentID so confirmation prompts and success messages still show the original INC-xxx format.
• Adds 9-case unit tests for the normalizer and two integration tests verifying the correct API path is called for both sequential IDs and UUIDs.

Confidence Score: 4/5

Safe to merge; the core normalization logic is correct and well-tested, with only a minor UX inconsistency in how error messages for get surface the original ID.

The normalization regex, its placement, and the split between displayID/incidentID in delete and update are all correct. The one gap is get.go, which discards the original input before the API call — so a 404 error message will reference the bare number rather than the user-supplied INC-xxx. This is a display inconsistency rather than a functional bug, but it goes against the PR's own stated goal of preserving the user-facing format.

internal/cmd/incidents/get.go — the original input ID is not retained for error message display

Important Files Changed

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
internal/cmd/incidents/get.go:39-40
The PR's stated goal is for user-facing messages to keep the original `INC-xxx` format, and `delete`/`update` both achieve this via a separate `displayID`. In `runGet`, only the normalized `id` is stored, so a 404 error bubbles up as `"failed to get incident: incident not found: 999"` rather than `"incident not found: INC-999"`. Storing the original input and using it in the error wrapping keeps the UX consistent.

```suggestion
func runGet(cmd *cobra.Command, args []string) error {
	displayID := args[0]
	id := api.NormalizeIncidentID(displayID)
```

_{Reviews (1): Last reviewed commit: "🐛 fix: resolve incidents get/update/del..." | Re-trigger Greptile}